Published on LinkedIn May 18, 2026
Most senior leaders have sat through a status meeting where every workstream reported green, and everyone in the room knew the portfolio was in trouble. Nobody said what they knew. The meeting ended. The work continued. Nothing changed.
That is performance theatre. It is one of the most expensive patterns in organizational delivery, and it is almost never intentional.
Performance theatre is what happens when reporting systems are designed around compliance rather than decisions. The reports are accurate. The data is real. The dashboards update on schedule. None of it tells a senior leader what they need to do differently this week, which means it is consuming leadership attention without producing leadership value.
The distinction matters more than most organizations acknowledge. Compliance reporting answers one question: Did we do the thing we said we would do? It confirms activity, demonstrates adherence to the process, and creates a record. These functions have their place. They become performance theatre when they occupy the space where decision-support reporting should be.
Decision-support reporting answers a different question: what does leadership need to know right now to make a better decision than they would make without this information? That question produces a fundamentally different kind of artifact. It surfaces risk before it becomes a crisis. It identifies where decisions are being delayed and what is waiting on them. It distinguishes between what is moving and what is stalled, and it names the cause with enough specificity that someone can act on it.
In a 1967 paper in Management Science, Russell Ackoff introduced the concept of management misinformation systems. His argument was that most management information systems give leaders what they ask for rather than what they need. Organizations build reporting infrastructure that produces accurate data about the wrong things, then use that data to make decisions as though the picture were complete. The accuracy of the data becomes its own problem because it creates confidence in an incomplete picture.
The green dashboard problem is a direct expression of this. When reporting systems measure milestone completion, budget adherence, and scheduled deliverables, they produce accurate information about outputs. They frequently tell you nothing about whether those outputs are moving toward the right outcome, whether the delivery team is absorbing unsustainable pressure to maintain those numbers, or whether a risk that has been visible for three weeks is about to become a crisis. The portfolio looks healthy on paper, but not in practice.
Performance theatre accumulates for predictable reasons. Reporting cadences get designed to satisfy governance requirements rather than to support the decisions governance exists to make. Teams learn that green reporting produces fewer questions, so they calibrate their communications accordingly. Leaders accept the reporting because challenging it requires a different conversation than most governance structures are built to hold.
Decision-support reporting requires three things that compliance reporting typically avoids. Honest risk surfacing: naming what is uncertain or at risk with enough specificity that a decision can be made about it. Decision visibility: identifying where approvals, resources, or direction are being waited on and how long they have been in that state. And a clear distinction between activity and progress: separating the volume of work happening from movement toward outcomes that actually matter.
None of these are technically difficult. They require a different design intent. The reporting system has to be built around the question of what decisions it needs to support, not around what information is available to report.
The diagnostic is straightforward. Look at the last three senior leadership reports your organization produced. For each one, identify a decision that was made differently as a result of the information in that report. If you cannot identify one, the reporting is compliance documentation. It may be accurate and well-produced, but it is not management information.
That exercise is uncomfortable because the honest result in most organizations is that reporting consumes significant effort to produce and generates very little decision value at the top. The cost is not only in the hours spent preparing reports. It is in the decisions that were not made because the information needed to make them was not surfaced in a format that leadership could act on.
Organizations that close this gap treat reporting as a design problem. They start with the decision: what does a senior leader need to know to act differently? Then they build the reporting structure to reliably surface that information. That approach produces leaner, more specific, and considerably more useful management information than building from available data forward.
Reporting that cannot change what leadership does next is not management information. It is documentation with a distribution list.
Strategic Signals publishes monthly on strategy systems and execution clarity for senior leaders. Subscribe to receive each issue directly. Subscribe
If this piece resonated, ALIGN: The Leadership Framework for Clarity in Complex Organizations is available on Amazon. Click Here.
